[VIndex V1] Resolve concurrency concern using Predict API - #137
Merged
Conversation
Contributor
Author
|
Hold on, I just realized I ended up with 2 branches on top of each other here. Back in a sec. |
mhutchinson
force-pushed
the
docs/v1-predict
branch
from
June 17, 2026 09:50
d01d026 to
94081d4
Compare
mhutchinson
changed the title
mhutchinson
force-pushed
the
docs/v1-predict
branch
from
July 27, 2026 12:48
94081d4 to
fdf709a
Compare
AlCutter
approved these changes
Jul 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously there was a large question mark around how concurrency would work with the output log and MPT. This is now resolved.